OpenEdge Getting Started:<br />Installation and Configuration Preface

This book describes installation and configuration topics related to the OpenEdge® Release 10.1A for the following operating systems:

Windows 2000, Windows 2003, and Windows XP Professional.

Note: Virtualization software, such as Citrix Presentation Server and VMware, are not described in this manual. Details about virtualization software support are documented in OpenEdge 10 Platform and Product Availability Guide.

UNIX and Linux.

Note: Unless otherwise noted, platform references throughout this guide have been simplified for readability. Windows refers to Windows 2000, Windows 2003, and Windows XP Professional. Similarly, UNIX refers to UNIX and Linux.

Audience

Administrative and technical personnel responsible for installing and configuring OpenEdge Release 10.1A.

Organization

Lists system and platform prerequisites and requirements for installing OpenEdge on Windows.

Lists system and platform prerequisites and requirements for installing OpenEdge on UNIX.

Identifies prerequisite information to know and preliminary tasks to perform before you install OpenEdge software on Windows or UNIX.

Contains information related to installation and postinstallation tasks for OpenEdge in Windows platforms. (The detailed procedures to complete the Installation Utility are presented only in the Windows online help.)

Contains information related to installation and postinstallation tasks when installing OpenEdge on UNIX platforms. (The detailed procedures to complete the Installation Utility are presented only in the UNIX online help.)

Provides step-by-step instructions to perform a variety of administrative tasks and describes how to manage Windows and UNIX platform-specific resources, respectively.

Describes how to use OpenEdge utilities to manage key stores for OpenEdge servers and manage certificate stores for OpenEdge clients.

Introduces the Progress Explorer framework, and highlights the framework’s elements. Also describes how to manage property files using the mergeprop utility.

Further describes the common framework and tasks to configure the common components of the OpenEdge Unified Broker products.

Provides instructions to start and connect to an OpenEdge RDBMS in different modes. Also provides information about running OpenEdge clients and servers on a network.

Identifies all possible components and subcomponents associated with each product that can be installed in a Windows environment.

Identifies all possible components and subcomponents associated with each product that can be installed in a UNIX environment.

Provides a planning tool to determine and record product installation choices on Windows before running the OpenEdge Release 10.1A Installation Utility.

Provides a planning tool to determine and record product installation choices on UNIX before running the OpenEdge Release 10.1A Installation Utility.

Describes commands and utilities whose primary syntax and functional documentation is in this manual.

Presents additional detailed information about the NameServer load balancing feature.

Provides information about different configuration models you can reference and details about running OpenEdge installations in a network environment.

Provides additional information to use the Adminserver to determine the data logged in the AdminServer log and to set authentication to start servers administered by the AdminServer.

Using this manual

The main topics presented in this guide also work with or point to related installation or configuration details presented in other OpenEdge documentation.

Installation planning and performing

Familiarize yourself with the installation information and tasks for your operating system by proceeding as follows:

Read the chapters in Part I, Installation in chronological order to help you plan and perform your installation.

Reference the information provided in Part III, OpenEdge Products and Components that provides preinstallation checklists, and product component and subcomponent details.

Obtain a copy of the installation online help. Reference Table 3–1 for detailed information about where you can locate a copy of the online help.

Configuration concepts

Part II, Configuration presents general OpenEdge configuration concepts and arrangements. Reference details presented in these chapters:

As needed, these chapters point to other product documentation for configuration details.

Typographical conventions


Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge® key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
`Fixed width`	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
`Fixed-width italics`	Fixed-width italics indicate variables in syntax statements.
`Fixed-width bold`	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.
[ ]	Large brackets indicate the items within them are optional.
[ ]	Small brackets are part of the Progress 4GL language.
{ }	Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams.
{ }	Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure.
\|	A vertical bar indicates a choice.
...	Ellipses indicate repetition: you can choose one or more of the preceding items.

Examples of syntax descriptions

In this example, ACCUM is a keyword, and aggregate and expression are variables:

Syntax
ACCUM `aggregate expression`

FOR is one of the statements that can end with either a period or a colon, as in this example:

FOR EACH Customer: DISPLAY Name. END.

In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional:

In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item:

A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example:

Syntax
DISPLAY [ STREAM `stream` ] [ UNLESS-HIDDEN ] [ NO-ERROR ]

Syntax
INITIAL [ `constant` [ , `constant` ] ]

Syntax
{ `&argument-name` }

In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them:

In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas:

Syntax
PRESELECT [ EACH \| FIRST \| LAST ] `record-phrase`

Syntax
MAXIMUM ( `expression` , `expression` [ , `expression` ] ... )

In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) ], and any number of additional expression or SKIP [ ( n ) ] is allowed:

Syntax
MESSAGE { `expression` \| SKIP [ ( `n` ) ] } ...

In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }:

Syntax
{ `include-file` [ `argument` \| `&argument-name = "argument-value"` ] ... }

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.

Syntax
WITH [ ACCUM `max-length` ] [ `expression` DOWN ] [ CENTERED ] [ `n` COLUMNS ] [ SIDE-LABELS ] [ STREAM-IO ]

Complex syntax descriptions with both required and optional elements

Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements).

In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets:

Syntax
ASSIGN { [ FRAME `frame` ] { `field` [ = `expression` ] } [ WHEN `expression` ] } ... \| { `record` [ EXCEPT `field` ... ] }

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.

Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.

Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.

Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.

Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.

Terminates the current session.

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

** Unknown table name `table.` (200)

Choose Help

Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.

Choose Help

Messages and then type the message number to display a description of a specific OpenEdge message.

In the Progress Procedure Editor, press the HELP key or F1.

On UNIX platforms, use the Progress pro command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number.

Start the Progress Procedure Editor:


`install-dir`/dlc/bin/pro

Press F3 to access the menu bar, then choose Help

Messages.

Type the message number and press ENTER. Details about that message number appear.

Press F4 to close the message, press F3 to access the Progress Procedure Editor menu, and choose File

Exit.

Preface

Purpose